Repository navigation
Document customer-managed executors on Sourcegraph Cloud - #2138
Merged
Merged
Conversation
Adds a Customer-managed executors section to the Cloud page: Cloud runs executors by default, and customers can ask their account team to run them in their own Google Cloud or AWS account with the same Terraform modules as self-hosted instances. It covers the dedicated allowlisted executor endpoint, the values Sourcegraph sends for the Terraform module, and the shared responsibility for availability and static egress IPs. Links the section from the admin executors Cloud callout, the self-hosted executors landing page, and the Terraform deployment guides, so a Cloud reader can find the Terraform modules. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-c2c49e6a-8194-4e78-9204-53c7b947eca6
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Direct preview links to pages changed in this PR: |
Contributor
This comment has been minimized.
This comment has been minimized.
enriquegh
enabled auto-merge (squash)
November 6, 2026 01:02
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docs never explained customer-managed executors on Sourcegraph Cloud. This adds a short Customer-managed executors section to /cloud and links to it from the executor pages.
The new section covers:
/.executors/on port 443 and the executor container registry on port 5000.executor_sourcegraph_external_urlandexecutor_sourcegraph_executor_proxy_password.The section also says this feature is separate from Private Connectivity (Sourcegraph Connect, PrivateLink, PSC).
These details come from
sourcegraph/controller:internal/resource/executor/customer_managed_executors.goand the customer setup email that the Cloud dashboard sends (internal/instances/dashboard/).The self-hosted executors landing page already lists Terraform on AWS and Google Cloud as recommended deployment methods. The gap was on the Cloud side, so this PR adds one-line pointers to the new section in these places:
/admin/executors/self-hosted/executorslanding pageTest plan
pnpm run check links --check-anchors --check-self-linksagainst the merge-base baseline reports no new dead links.dev/check-hostnames.mjson the diff reports no issues.dev/check-duplicates.mjsflags only the auto-scaling note in the AWS and Google Cloud guides. That note was already duplicated, and this PR does not change it.